S;_πjS∨_πI←≠@
Ck8↓|Y:λ	αK"_∧(←3_
iNx∂wa≠@
∧GN0αlY:`	≠Y:p	9G20α)IN_βbK?0∧,M>p¬dkNλ⊂9G⊗0α∧S∩hπ*IN`βyM?0¬zhE_∂/INx∧∂[;_	igR_∂!SZ_λ5K2_∧'g≠(∞λa∨_
¬KNp∧GMN0ε∞Y&HλOMNHε↔S"_πFM2(εe∞0
K3_∧)M⊗(ε
a"_
α]fH
Y:_	⊗←∨_
S?0πteV_
be∂(
≥←↔@
Y∪_λG]⊗ q←M⊂
QN`ε SN πK& ∧≤C7↓([∪_	IS2_πEg:_∞#M&λ¬5SNpλ∞S2HπJG60α?a2_
↓SO λ$←2_
N(ε
;∞JM&p¬Pe∨_
<[?0	z←⊗`
←⊗h
]∞`∪←"_

↔_
iR0⊂∃g:`∞<]⊂
tK7_∧;S
π∧←"p
:←?0
a⊗0
:_↓8[O_
K≠@∧*RR π↓]⊗⊂Ra3_
βQR`εkKc∧US6λπ←Kc_∧oaN0
εi∪_∂?RS_παRS πβS~ π:kN_⊂JSS λ-M∞ ¬βM∞0¬_SNxλ∂SOλ∃Y' λc[C_
∨CJ`↓AS3_πGG;8αeS≠@πHg>(∞hI;_α|IWP∧⊂Y&hλ][R⊂
Ge⊗ 
.Y6pλ|QNxεGIJ_β9]∂@7K∨_∧+S∞Hπ"kJ_⊂$SBxπz[S_
e↔⊂
i⊗_∂Ta
[Jp
MJ(ε
Np∞v←6p
LgO ∂πg&0
n←~p
x
⊃∨⊂h⊃⊃⊗⊃%⊃0⊃>⊃N⊃t⊃y∩α∩
⊂∩_∩*∩3∩C∩U∩]∩c∩k∩s∩}∪λ∪≠∪)∪?
⊃⊃⊃⊗⊃%⊃0⊃>⊃N⊃t⊃y∩α∩
⊂∩_∩*∩3∩C∩U∩]∩c∩k∩s∩}∪λ∪≠∪)∪?
h⊃⊃⊗⊃%⊃0⊃>⊃N⊃t⊃y∩α∩
⊂∩_∩*∩3∩C∩U∩]∩c∩k∩s∩}∪λ∪≠∪)∪?
⊃⊃⊃⊗⊃%⊃0⊃>⊃N⊃t⊃y∩α∩
⊂∩_∩*∩3∩C∩U∩]∩c∩k∩s∩}∪λ∪≠∪)∪?	The user  has  loaded  ALGOL  procedures  without  a  main
	program.   Execution will be terminated because of missing
	start address and undefined symbols.∪V	LINK-10 expected a particular user address to be in  core,
	but it is not there.>More than one successor link  satisfies  a  call  from  an
	ancestor  link.  At run time, the link in core, or the one
	with the longest path in core, will be used to satisfy the
	call.   No message will be given.  However, if none of the
	successor links are in core, the overlay handler picks one
	with  the  longest  path in core.  If all paths are equal,
	the overlay handler  picks  one  at  random  and  gives  a
	warning message to the user.  To avoid this situation, the
	user  should  promote,  to  a  common  link,  the   module
	containing the called subroutine.∪V	LINK-10's space allocator was called with  a  request  for
	zero words.	All attempts to obtain more core, including writing  files
	onto  disk,  have  failed.   The  program  is  too big for
	available user core, probably because of too  many  global
	symbols.  A future version of LINK-10 will overflow global
	symbols to the disk.  However,  there  will  always  be  a
	minimum size below which LINK-10 will not operate.	This message occurs when the user changes  the  device  on
	which  the  log  file  is  being written.  The log file is
	closed on the first device and the remainder of  the  file
	is written on the second device.	The COBOL-produced file must be the first file loaded when
	loading   COBOL  modules.   COBDDT,  the  COBOL  debugging
	program, or any other modules, such as  a  MACRO  routine,
	cannot  be the first file in the command string.  The user
	should begin  loading  again  and  place  the  COBOL  main
	program  or  routine  as  the  first  file  in the command
	string.∪V	The user attempted a feature that is not yet  implemented.	LINK-10 is generating the requested save file  by  running
	the  core image through a zero compressor routine in order
	to produce a SAV format file.	A device switch, such as /REWIND or /BACKSPACE,  has  been
	given,  but  there  is no device to be associated with it.
	The switch is ignored.  This occurs when the user does not
	give  a  device  name  in the specification containing the
	switch or has not specified a device name in  the  current
	line.   (Remember  that  devices are cleared at the end of
	the line.) LINK-10's default device DSK does not apply  to
	device  switches nor does a device specified in a /DEFAULT
	switch apply.  The user should respecify the command  line
	and include the appropriate device name with the switch.	The user is  reducing  the  size  of  an  already  defined
	relocation  counter via the /SET switch.  The new value is
	accepted.  The user should be extremely  careful  when  he
	does  this  because  code  previously loaded under the old
	relocation counter may be overwritten.  This  practice  of
	reducing  counters  is  dangerous  unless  the  user knows
	exactly where modules are loaded.	The user has a DATA statement in FORTRAN which sets  up  a
	COMMON area, but the COMMON area is in another link closer
	to the root.  The user should set up the  COMMON  area  in
	the link in which it is first defined.	The  user  has  a  data  store  to  an  absolutely-defined
	location that is not in the specified link (e.g., the user
	is storing data in  JOBDAT).  The  user  should  move  the
	module to the root link.∪[∪n	On an internal check of the counter for undefined symbols,
	LINK-10 determined that the counter was negative.∀i	A read error has occurred on the input device.  Use of the
	device is terminated and the file is released.∪∪∪∪∪	LINK-10 could not create the overlay  file  on  the  disk.
	The user could be over quota, or the disk could be full or
	have errors.	Notification that the LINK-10 module LNKMAP has  completed
	the writing of the map file.  The map is now closed.∪n	The code to handle symbols longer than six characters  has
	not  been  completed.   This  code  will be available in a
	future release.	LINK-10 needs more core and is expanding to the  specified
	amount.   In  future  loads of the same programs, the user
	can run LINK-10 more efficiently by requesting this amount
	of  core  at  the  beginning  of  the  load with the /CORE
	switch.	LINK-10 is entering the completion stages of  the  loading
	process.   These  stages  include the creation of save and
	symbol files and, if required, the execution of  the  core
	image.∪n	Incorrect code was generated by the  F40  compiler  for  a
	data statement in the form
	     DATA A(I),I=1,4/1,2,3,4/
	as opposed to a data statement in the form
	     DATA (A(I),I=1,4)/1,2,3,4/	LINK-10  is  now  reading  the  low  and/or  high  segment
	overflow files backwards in order to do all remaining code
	fixups.   This  process  may   cause   considerable   disk
	overhead.   Note  that the message occurs only if the load
	was too large to fit entirely in core.	The FORTRAN-10 compiler generates different output for the
	KA10 and the KI10 processors (e.g., double precision code)
	and the user cannot load this mixture.  He  should  decide
	which  processor  he  wants  to use and then recompile the
	appropriate programs.	LINK-10 has completed  its  task  of  loading  the  user's
	program  and  other  required programs.  Control is either
	returned to the monitor or given to the user's program for
	execution.	Output from the F40 and  FORTRAN-10  compilers  cannot  be
	used  together  in  the same load.  The user should decide
	which compiler he wants and then recompile the appropriate
	program with that compiler.	Output from the F40  compiler  cannot  be  used  with  the
	overlay  facility.   The user should recompile his program
	with the FORTRAN-10 compiler.@q@@↓
↓~	LINK-10 cannot find the return  instructions  in  the  F40
	compiled subroutine.	The user gave a /FORSE  switch  while  loading  FORTRAN-10
	compiled code.	The user is trying  to  set  the  beginning  of  the  high
	segment below the end of the last page of the low segment.
	The user can either specify a /SET:.HIGH.   switch  or  in
	the  case  of MACRO-10, reassemble the module.  (Note that
	the setting of the beginning of  the  high  segment  below
	400000 will fail on all KI10 monitors previous to 5.07 and
	on all KA10 monitors.)	The user is attempting to change the starting  address  of
	the  high  segment.   The specified value is ignored.  The
	cause may be that  the  user  gave  a  /SET:.HIGH.:  value
	switch  which does not agree with the LINK item type 3, or
	that two LINK item type 3's have different  origins.   The
	user should recompile the incorrect files.∪n	The user has more global  symbols  than  can  fit  in  the
	maximum  hash  table  (about  25K  in  size)  LINK-10  can
	generate.  Possible action  is  to  increase  the  maximum
	allowable size of the hash table.∪[∪[∪[	An attempt was made to expand the blank COMMON area.  Once
	a  COMMON  area  is  defined, the size cannot be expanded.
	The user should load the module  with  the  largest  blank
	COMMON  area  first  or  specify  the larger area with the
	/COMMON switch before loading either module.	There is not enough  core  in  the  system  to  initialize
	LINK-10.	The data mode specified for a device is illegal,  such  as
	dump  mode  for  the terminal (e.g., TTY:/SAVE).  The user
	should respecify the correct device.	The OPEN or INIT UUO failed for the specified device.  The
	device could be in use by another user.∀~∀~∀~∀~∀~	The input file either was generated by a  translator  that
	LINK-10   does   not   recognize  (e.g.,  a  non-supported
	translator) or is not in proper binary format (e.g., is an
	ASCII or SAV file).	The  INCREMENTAL  keyword  for  the  /MAP  switch  is  not
	implemented.  The switch is ignored.∪V	LINK-10 attempted to do I/O (LOOKUP,  ENTER  UUOs)  for  a
	channel  that  has  not  been set up.∀i	An error occurred when reading the overlay file.∪V	An incorrect link  item  type  11  was  seen.	An  already-defined  symbol  has  been  given   a   second
	"partial"  definition.   The user should examine the usage
	of the named symbol.∪n∪V	An incorrect link  item  type  11  was  seen.∪n	The current symbol pointer  does  not  point  to  a  valid
	symbol triplet.  This can occur if an extended symbol does
	not terminate  properly.∪n	An internal error occurred in the switch tables  built  by
	the SCAN module.	A number other than 1 through 20 was used in a  link  item
	type 12.∪n	The range checking of LINK-10's internal tables and arrays
	failed.    The   address   output  is  the  point  in  the
	appropriate LINK-10 segment at which this occurred.	Indication that the LINK-10 module LNKLOD has started  its
	processing.	The index (link item type 14) on a FUDGE library  file  is
	not  correct.   The  file will be searched as if the index
	were absent.	LINK-10 has begun its processing of the user's input.	An error occurred in the  named  link  item.   This  could
	result  from  incorrect  output  generated by a translator
	(e.g., no argument is seen on an END  block  when  one  is
	required).  The user should retranslate the module.	LINK-10 is in the process of loading the named module.	The user has previously assigned  the  specified  name  to
	another  link.   This attempt is ignored.  The user should
	specify a different name if he wants one  associated  with
	the link.∪n	The named link could not be found in core.	The indicated link has not  yet  been  loaded.   This  can
	happen if the user specifies link numbers, instead of link
	names, as arguments to the /RESET switch and then  forgets
	the  numbers.   The  /RESET switch is ignored.  The use of
	link numbers as arguments is not recommended.	The user specified a name of a link on the  /RESET  switch
	and LINK-10 has not yet loaded a link with that name.  The
	/RESET switch is ignored.	The user has given  an  existing  global  symbol  a  value
	different from its original one.  The second occurrence of
	the global symbol is in the named module.   The  currently
	defined value is used.  The user should change the name of
	the symbol or reassemble one of the files with the correct
	parameters.	Alphabetic and numeric sorting of the map file is not  yet
	implemented.   The  symbols  appear  in the order in which
	they were placed in the symbol table.	This message indicates that LINK-10 is making  inefficient
	use  of  core.   In future loads of the same programs, the
	user should allocate more core to LINK-10 at the beginning
	of  the load.  Area is one of the following: LC=user's low
	segment code, HC=user's high segment code, LS=local symbol
	table, FX=fixup area, and GS=global symbol table.	Indication that the LINK-10 module  LNKMAP  has  begun  to
	write a map file.	Overlay structures consisting of more than one region  are
	not yet supported.	The current value of MAXCOR is too small  for  LINK-10  to
	operate.   In  future  loads of this program, the user can
	save LINK-10 time by setting MAXCOR to this  new  expanded
	size at the beginning of the load.	The user attempted to set MAXCOR to a value so large  that
	the  low  segment  would  be greater than the start of the
	high segment.  The value of n is usually 128K.	The user specified the /MAXCOR  switch  with  an  argument
	that is below the minimum size LINK-10 requires as its low
	segment.  The switch is  ignored.   The  minimum  size  is
	dependent  upon  the code already loaded.  The user should
	respecify the switch.	The user attempted to  move  LINK-10  backwards  from  its
	current position on the path to a position beyond the root
	link.  For example, if LINK-10  is  positioned  after  the
	fourth  link  in  a  path, the largest negative number the
	user can specify as an argument to the /NODE switch is -3.	The user's program was too large to load into core.  Thus,
	LINK-10  created  a  saved  file  on disk and cleared user
	core.  The user can perform a GET or RUN operation on  the
	program  to load it into core.  If the core image is still
	too big, the user can either employ a  bigger  machine  or
	obtain a larger core limit (e.g., increase CORMAX).	The user's program was too large to  load  into  core  and
	LINK-10  created  a  saved file on disk.  It automatically
	executes the program by performing a  RUN  UUO.   However,
	the  saved  file  remains on disk and the user must delete
	it, if he wishes.	The end block (type 5) has not been  seen  for  the  named
	module.   This  can happen if two name blocks (type 6) are
	seen without an intervening end block, or if  the  end  of
	the  file  was  seen  before the end block.  Although this
	message is not fatal, usually fatal errors follow.	The user has specified a device that does not exist in the
	system.   The  user can re-edit the input files to correct
	the device name or type control-C to abort the load.	The user issued a switch that is not implemented  in  this
	version of LINK-10.∀.∀.∀.∀.∀.∀B∀B∀B∀B	The standard released  version  of  LINK-10  includes  the
	LNKF40   module   that   loads  F40  code.   However,  the
	installation has removed it by loading a dummy version  of
	LNKF40  and  thus LINK-10 is unable to handle F40 compiler
	output.  The user should request his installation to  load
	a version of LINK-10 with the real LNKF40 module.∪n	The internal symbols in the overlay handler could  not  be
	referenced.   This  is  either an internal error or a user
	error if the user supplied his own overlay handler.	LINK-10 requires a monitor that contains the DEVSIZ UUO.∀i	An error has occurred while writing the overlay file.	Indication that the LINK-10 module LNKOV2  has  begun  its
	second phase of writing the overlay file.	The last address allocated  by  the  specified  module  is
	greater  than  256K. The user should modify the modules of
	his load list to reduce the  program  size  to  less  than
	256K.  This  error condition is usually caused by the user
	dimensioning arrays too large.∪n∀Q∀Q∀Q∀Q∀Q	The requested feature is not yet available.	The relocation counter table is a fixed length and  cannot
	be  expanded  in  the  current  version  of LINK-10.  This
	restriction will be eliminated in a future release.	The user has given a global symbol as  the  /SET   address
	and  the  symbol  is currently undefined.  The user should
	load the module that defines the symbol.	LINK-10's internal tables have been deleted and  core  has
	been  reclaimed.   This  message  occurs  near  the end of
	loading.	LINK-10 is expanding the global symbol table either to the
	next prime number as requested by the user (via /HASHSIZE)
	or to its next expansion of about 50%.  In future loads of
	this  program,  the  user can save LINK-10 time by setting
	the hash table to this new expanded size at the  beginning
	of the load.	This is the response to the /REQUEST switch.∪n	LINK-10's space allocator received some words that did not
	fit into the area to which they were to be returned.∪n	An internal LINK-10 error.   LINK-10's  hashing  algorithm
	failed.   A symbol already exists in the location in which
	LINK-10 needs to place the  new  symbol.   The  error  may
	disappear  if  the  user  loads  the  files in a different
	order.∪n	An internal LINK-10 inconsistency.  LINK-10 cannot  locate
	the  TITLE  triplets  in order to store the lengths of the
	control sections.  The  loading  process  continues.   Any
	maps requested by the user will not contain the lengths of
	the control sections.	The user has defined a non-COMMON  symbol  with  the  same
	name  as  a  COMMON  symbol.  The user should decide which
	symbol  definition  he  wants.   If  he  uses  the  COMMON
	definition, the COMMON area should be loaded first.	LINK-10 has completed the scanning and processing  of  the
	current  command  line and is ready to accept the input on
	the next line.	The named subroutine is not in a  successor  on  the  same
	path  as  the  calling  link, but is in another path.  The
	user should reconstruct his overlay  structure  and  place
	the  subroutine on the correct path.  Otherwise, a call to
	an undefined subroutine will occur at run time.∀i	An error has occurred on  the  save  file.   The  file  is
	closed  at  the end of the last data that was successfully
	output.	Alphabetic and numeric sorting of the symbol table is  not
	yet implemented.  The symbols appear in the order in which
	they were placed in the symbol table.	LINK-10  is  arranging  the  symbol  table  in  the  order
	specified  by  the  user  via  the  /SYSORT switch, and if
	required, is converting the symbols from the  new  to  old
	format  as  indicated  on  the /SYMSEG, /SYMBOL, or /DEBUG
	switch.	The symbol table has been sorted and  moved  according  to
	the  user's  request  via  the /SYMSEG, /SYMBOL, or /DEBUG
	switch.	LINK item type 13 (LVAR) is not implemented in LINK-10 nor
	supported  by  DEC.   The TWOSEG pseudo-op in the MACRO-10
	language should be used.	The /NOINITIAL switch was placed  in  the  command  string
	after  the  first file specification.  Because this switch
	was not first in the  command  string,  LINK-10's  initial
	symbol table was loaded.	An attempt was made to expand a COMMON area.  The  largest
	occurrence  of  the  COMMON  area  of a given name must be
	linked first.  Once defined, the size cannot  be  expanded
	although  new  COMMON  areas  of  different  names  can be
	defined.  The user  should  load  the  largest  occurrence
	first, or use the /COMMON switch.	The user attempted to force two segments into one  segment
	via the /SEGMENT switch.  However, the binary file dos not
	contain the necessary information (i.e., the length of the
	high  segment)  in  LINK  item  type 3.  This situation is
	usually caused by a one-pass compiler (e.g.,ALGOL).∪n	When LINK-10 produces the index for the map it  has  found
	more  program names than actually exist.  The symbol table
	is in error.	Bits 0-3 of the first word of the  link  item  contain  an
	unknown  symbol code.  Either the translator is generating
	incorrect code or the binary file is bad.  The user should
	recompile the file.	The user has given a global symbol as  the  start  address
	and  the  symbol  is currently undefined.  The user should
	load the module that defines the symbol.	A reference to the named subroutine has  occurred  in  the
	specified  link,  and  LINK-10  has  not  yet  loaded  the
	referenced subroutine.  If this subroutine is required for
	execution, the user should reload and include the required
	modules on the path on which they were referenced.	One of the following conditions occurred:

	1.  The filename given was illegal.

	2.  When updating a file, the filename given did not match
	    the file to be updated.

	3.  The RENAME UUO following a LOOKUP UUO failed.	The file requested by the user was not  found.   The  user
	should respecify the correct filename.	The UFD does not exist on the named file structure, or the
	project-programmer number given was incorrect.	The user does not have the correct  privileges  to  access
	the named file.	The directory on the DECtape has no room for the file.	Another user is currently modifying the named  file.   The
	user should try accessing the file later.	The specified filename  already  exists,  or  a  different
	filename  was  given  on  the ENTER UUO following a LOOKUP
	UUO.∪n	The user specified an illegal sequence of  monitor  calls,
	UUOs, (e.g., a RENAME without a preceding LOOKUP or ENTER,
	or a LOOKUP after an ENTER).∪n	One of the following conditions occurred:

	1.  Transmission, device, or  data  error  occurred  while
	    attempting to read the UFD or RIB.

	2.  A hardware-detected device or data error was  detected
	    while reading the UFD RIB or UFD data block.

	3.  A  software-detected  data  inconsistency  error   was
	    detected while reading the UFD RIB or file RIB.∪a	The named file is not a core image file.∪a	The system cannot supply enough core to use as buffers  or
	to read in a program.∪a	The  device  indicated  by  the  user  is  currently   not
	available.∪a	The device specified by the user  does  not  exist.∪a	The  machine  does  not  have  a  two-register  relocation
	capability.	There is no room on the file structure for the named file,
	or  the  user's  quota  on  the  file  structure  would be
	exceeded if the file were placed on the structure.	The user cannot write on the specified device  because  it
	is write-locked.	There is not enough table space in the monitor's  (FILSER)
	4-word blocks for the specified file.  The user should try
	running the job at a later time.	Because of the user's quota or the available space on  the
	device,  the total number of blocks requested could not be
	allocated and a partial allocation was given.∪a	The  block  required  by  LINK-10  is  not  available  for
	allocation.∪a	The user attempted to  supersede  an  existing  directory.∪a	The user attempted to delete  a  directory  that  was  not
	empty.	The required sub-file directory in the specified path  was
	not found.	A LOOKUP and ENTER UUO was performed on generic device DSK
	and the search list is empty.∪a	An attempt was made to create a subfile  directory  nested
	deeper  than  the maximum level allowed.	No file structure in the job's search list  has  both  the
	no-create bit and the write-lock bit equal to zero and has
	the UFD or SFD specified by the default or explicit path.∪a	A GETSEG UUO was issued from a locked  low  segment  to  a
	high  segment  which  is  not  a  dormant, active, or idle
	segment.∪a	A LOOKUP and ENTER UUO was given to update a file, but the
	file cannot be updated for some reason (e.g., another user
	is superseding it or the file was deleted between the time
	of the LOOKUP and the ENTER.	The end of the low segment is above the beginning  of  the
	high segment.∪n	This message indicates that a  LOOKUP,  ENTER,  or  RENAME
	error  occurred which was larger in number than the errors
	LINK-10 knows about.∪n	This is an internal LINK-10 error.∪n	Incorrect code has been generated by the F40 compiler.∪n	This  message  can  never  occur  and is included only for
	completeness of the LOOKUP, ENTER, and RENAME error codes.	This message is not expected to occur.  If it does, please
	notify   your  Software  Specialist  or  send  a  Software
	Performance Report (SPR) to DEC.	LINK-10  could  not  make  the  named  file  on  the  disk
	(LC=user's  low segment code, HC=user's high segment code,
	LS=local symbol table, FX=fixup area, and GS=global symbol
	table).   The  user could be over quota, or the disk could
	be full or have errors.∀i	An  error  occurred  while  reading  in  the  named   area
	(LC=user's  low segment code, HC=user's high segment code,
	LS=local symbol table, FX=fixup area, and GS=global symbol
	table).∀i	An  error  occurred  while  writing  out  the  named  area
	(LC=user's  low segment code, HC=user's high segment code,
	LS=local symbol table, FX=fixup area, and GS=global symbol
	table).∀i	An error has occurred on the output file.  The output file
	is   closed   at  the  end  of  the  last  data  that  was
	successfully output.	the job is too large to fit into the allowed core and  the
	named  area  is  being  moved to disk (LC=user low segment
	code, HC=user high segment code,  LS=local  symbol  table,
	FX=fixup area, and GS=global symbol table).	The status is represented by the right half  of  the  file
	status  word.  Refer to DECsystem-10 Monitor Calls for the
	explanation of the file status bits.